home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c++
- Path: netcom.com!NewsWatcher!user
- From: bastion1@netcom.com (Gregory & Jennifer Weston)
- Subject: Re: MFC or OWL?
- Message-ID: <bastion1-2503961918000001@10.0.2.15>
- Sender: bastion1@netcom16.netcom.com
- Organization: Bastion Products
- References: <DKKv8H.K35@iquest.net> <4i8od1$clt@Steinlager.tip.net> <4ipmh6$79g@btree.brooktree.com> <1996Mar25.132903.546@friend.kastle.com>
- Date: Tue, 26 Mar 1996 00:18:00 GMT
-
- In article <1996Mar25.132903.546@friend.kastle.com>, rich@kastle.com wrote:
-
- >>>MFC is the industry standard...
- >>Says who ? Computer press or/and uneducated managers ?
- >Says virtually all Windows C++ compiler vendors. Apparently they are
- >beginning to agree with Microsoft's assertion that MFC is a de-facto
- >standard, because they are all licensing MFC for inclusion in their
- >compiler products. The only serious competitor to MFC was Borland's
- >OWL, but as of Borland C++ 5.0, MFC class libraries are also included.
-
- Um, no. BC++ 5.0 can compile MFC stuff, but they do not actually include
- the MFC. MS' licensing is too restrictive to allow that. I still stand by
- my earlier assertion that OWL is a significantly higher quality C++
- framework than MFC, and I'll choose quality over quantity any day.
-
- Greg
-
- --
- *** Bastion Products: Where classic quality meets modern technology. ***
- Well, in fact, this post DOES represent the opinions of Bastion Products.
- How's that for a switch?
-